rfc: renaming types and fields for remote schemas #4821
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tirumaraiselvan
force-pushed
the
rfc-renaming-types-fields
branch
from
42bf527
to
12614ca
Compare
|
Deploy preview for hasura-docs ready! Built with commit c112c77 |
|
Do you guys have a deadline for this? |
tirumaraiselvan
changed the title
tirumaraiselvan
force-pushed
the
rfc-renaming-types-fields
branch
from
c112c77
to
f0fe7cd
Compare
tirumaraiselvan
force-pushed
the
rfc-renaming-types-fields
branch
from
f0fe7cd
to
97dce4b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Functionality and API spec for allowing changing type names and field names of generated schema for Remote Schemas.
View it here: https://github.com/tirumaraiselvan/graphql-engine/blob/rfc-renaming-types-fields/rfcs/renaming-types-and-fields.md
Related issues:
#3518
#5863